Apple is developing "Universal Asm Interfaces". They are not yet complete, we are supplying them here in as-is. They can be used with PPCAsm (1.1d5 or later) for PowerPC development or with Asm for classic 68K development. These files are radically different than previous AIncludes. They now parallel the C and Pascal headers. There is a one-to-one mapping between the files in AIncludes and those in CIncludes. Every struct in C is now a RECORD in asm. Every constant in C is now an EQU in asm. Every function prototype in C is now an 68K macro or import in asm.
Important: The new AInclude files do not support CFM 68K development in this release.
Important: The new AInclude files have new names which parallel the C headers (e.g. Files.a). If you wish to continue using the old style AIncludes (for 68K), just continue to include the old names in your source files (e.g. FSEqu.a).
Important: Traps.a now longer contains all the macros/opwords for all toolbox traps (e.g. _GetResource). Instead the interface file for each manager declares its macros (e.g. _GetResources is now in Resources.a)
Important: The macros for low-mem accessing use pascal calling conventions (just like the C and pascal accessors use). In the next release, the macros will allow direct (i.e. Move.l $02F0, D0) access to low-mem locations for classic 68K runtime.
Important: Be wary about mixing Universal AIncludes and the old style AIncludes. Many of the file names are the same, but have a different contents, and they each auto-include different other files. If you decide to use the Universal AIncludes, completely replace your AIncludes folder - do not back up into it. Then add back any contents, or files as you discover they are needed.
Note: The Asm tool limits include file depth to 5 levels. The Universal Asm files have their auto-includes organized to work around this limit. You can include any system (.a) file from your source file in any order. But, you might have problems if you have your own “interface” file which includes system interface files. If you do and run into the limit, rearrange the includes in your interface file. For example, adding an include of Memory.a before including Windows.a will reduce the include depth.
